<paroneayea> ----------------------
<paroneayea> MEETING LOGGING STARTS
<paroneayea> ----------------------
<paroneayea> hiya all!
<ShawnRisk> hi                                                          [11:06]
<paroneayea> first meeting topic, Chris needs to push up all those meeting
             logging backlogs :)
*** chimo (~chimo@CPE001e5822f752-CM0012c9ab559e.cpe.net.cable.rogers.com) has
    joined channel #mediagoblin
<paroneayea> heya chimo!  the meeting is just starting
<paroneayea> just to get a sense: who all is here?
<chimo> Hi! :)
* paroneayea is here ;)
* schendje present
<ayleph> hello
* Tumulte writing something                                             [11:07]
* Tumulte has troubles with grammar
<ShawnRisk> *faces the jury*
<paroneayea> :)
<paroneayea> well people can continue to announce their presence if they like,
             but in the meanwhile, I'm putting the agenda out here:     [11:08]
<paroneayea> http://wiki.mediagoblin.org/Meeting#Next_Meeting
* frewsxcv94709 raises his hand
<paroneayea> that's plenty to discuss this meeting!
<Tumulte> Joy.
<paroneayea> okay, so, I guess we should get right into it!
<paroneayea> First topic of conversation is bug triage day.             [11:09]
<paroneayea> so ShawnRisk raised this for the meeting, and I think it's a good
             one
<pythonsnake> Hi                                                        [11:10]
<paroneayea> for background, our current bug triage setup is every other
             thursday we do bug triage day, which is usually that shawnrisk
             finds some neglected tickets for people to go through with him
<paroneayea> ShawnRisk: want to make some comments on this since you were the
             one who raised it?
<ShawnRisk> Some days I am having trouble keeping up with everyone as there
            are 2 or 3 or 4 people at the same time.
<schendje> that's a good problem though, right?                         [11:11]
<ShawnRisk> Yes but I am over managed
<pythonsnake> Why thursday, btw? Why not weekend?
*** aegibson (62eae098@gateway/web/freenode/ip.98.234.224.152) has joined
    channel #mediagoblin
<paroneayea> pythonsnake: somewhat arbitrary; I forget why we chose that.
<ShawnRisk> I think we were looking for a day and Thursday worked out for most
            people at that time
<paroneayea> I think it's still working well it seems?                  [11:12]
<ShawnRisk> for the most part
<paroneayea> if the problem is shawnrisk having trouble keeping up with things
             I assume it's going well in that regard
<paroneayea> ShawnRisk: also this is a newish change, I think previously you
             were having trouble getting people to help you with tickets, and
             recently it's been the opposite; is that true?
<paroneayea> so there may be some issues with how to balance it         [11:13]
<paroneayea> it's also true probably that we do ticket triage very differently
             than other groups.
<ShawnRisk> Somewhat, I still have that problem.  Sometimes you are not here
            or sometimes others are not up to doing this.
<ShawnRisk> Also people have very different ideas on what this day is for.
            Some people use this to take over tickets, some use this to update
            tickets and others use this to put tickets in there to-do list.
<paroneayea> right                                                      [11:14]
<paroneayea> maybe one thing we should do
<ShawnRisk> What I would like to see is that tickets actually get updated on
            ticket triage days
<paroneayea> is to look at how other projects do ticket triaging?
<pythonsnake> ShawnRisk: that'd take time
<ShawnRisk> I know how Mozilla does that
<paroneayea> ShawnRisk: part of the issue is that giving a good update tends
             to involve a lot of research.                              [11:15]
<ShawnRisk> pythonsnake: I know but that is what the day is for
<paroneayea> and we don't want to just noise up the tickets
<paroneayea>
             https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/
<paroneayea> the django project has some ticket triaging workflows
<pythonsnake> ShawnRisk: fixing a bug in one day is not easy
<paroneayea> yes I think we have to accept the fact that we can't always give
             updates to every ticket
<paroneayea> and just making an update for updates' sake is going to make the
             situation worse                                            [11:16]
<paroneayea> a
<paroneayea> ticket with a lot of noise on it is very difficult to work on
             later
<paroneayea> what shawnrisk has done really well at is finding tickets that
             need attention; that's definitely valuable
<ShawnRisk> yep for sure
<paroneayea> so one thing I've noticed about
             https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/
                                                                        [11:17]
<paroneayea> and having submitted tickets to that project
<paroneayea> is they use the status of their tickets a lot better than we do
<paroneayea> currently we've started using the "review" ticket
<paroneayea> er, tag
<paroneayea> but maybe that should actually be a state of the ticket
*** minaeid90 (~minaeid90@41.42.219.41) has quit: Read error: Connection reset
    by peer
<paroneayea> see how django has all those states above for open tickets vs
             closed tickets
<ShawnRisk> I still believe that from my point of view is that if people take
            on a ticket, I don't know what they are doing with this.  I can't
            tell if this means they are looking at this or in their to-do list
            or something else.  Everyone's to-do list is huge.          [11:18]
<paroneayea> ShawnRisk: right
<pythonsnake> ShawnRisk: does it matter?
*** BjarniRunar (~bre@31-209-193-120.dsl.dynamic.simnet.is) has joined channel
    #mediagoblin                                                        [11:19]
<ShawnRisk> Nope, but makes me feel like I find tickets and then they go into
            the world of unknown
<paroneayea> ShawnRisk: that's maybe something that's not resolvable by just
             saying "look at these five tickets": one of several things will
             happen with a difficult ticket:
<paroneayea>  - either someone will possibly spend the whole day working on
             one update
<paroneayea>  - someone will just end up adding useless updates to a ticket
<paroneayea>  - a person will put it on their personal todo list to do later
<paroneayea> ShawnRisk: what I think we should do
<Tumulte> Can't we monitor tickets statistic to, at least, make sure the
          solving remain steady
<paroneayea> is look at what other projects are doing
<paroneayea> we should ping greg-g
<paroneayea> :)                                                         [11:20]
<ShawnRisk> I also feel that Mozilla does this well as they have a white board
            and different people can take the lead of the day on different
            hours.  They also list what has been updated, changed or happened
            that day with tickets.
<paroneayea> ah
<paroneayea> ShawnRisk: can you provide documentation on that?
<ShawnRisk> let me see
<AVRS> ShawnRisk: do you mean testdays or some non-Firefox bugdays?
<paroneayea> ShawnRisk: I think I'm getting the sense that this is a "we need
             to adjust our workflows", and that means that this conversation
             is going to take more than this hour.                      [11:21]
<AVRS> (Firefox bug triage isn't being done like that now.)
<paroneayea> ShawnRisk: I think we should pull together some information on
             how other projects are doing triaging and use that to re-evaluate
             what we're doing?
<paroneayea> AVRS: oh, how is it done?
<AVRS> paroneayea: https://etherpad.mozilla.org/qa-desktop-triage2013
<paroneayea> thanks AVRS 
<AVRS> The untriaged (unconfirmed and in the Untriaged component) bug list is
       split into groups of 10, and people assign the groups to themselves and
       look through them.                                               [11:22]
<paroneayea> ah
<AVRS> We don't record the changes to individual bugs there.
<ShawnRisk> AVRS: you are right
<paroneayea> AVRS: so this is also very different to how we're doing things;
             generally what ShawnRisk does is find tickets and ask to go
             through them with a specific person                        [11:23]
<AVRS> But on testdays, people do record what they do.
<paroneayea> whereas you're saying that triagers are evaluating the state of
             the tickets themselves(?)
<paroneayea> is there interaction between the person triaging and other devs?
<AVRS> That triage on Tuesdays is specific to UNCO bugs in the Untriaged
       component.
<paroneayea> how does that work?
<AVRS> On testdays, there is interaction.
<Elrond> (Okay, I'm now mostly here too)                                [11:24]
<AVRS> The Tuesday triage seems to just be formalized like that now, with
       almost no IRC interaction, but yes in the bugs.
<ShawnRisk> good to know
<pythonsnake> so add another day for checking state of the ticket?
*** Tumulte (~Tumulte@ALyon-651-1-231-18.w90-14.abo.wanadoo.fr) has quit:
    Remote host closed the connection
<AVRS> pythonsnake: if you mean Mozilla, that's a bit difficult; there is a
       verification day for fixed bugs, but there are so many bugs that it's
       not really feasable to have full lists.  Testdays have some
       topic-specific lists though.                                     [11:25]
<ayleph> It sounds like there's confusion over what "triage" means. Triaging
         is the process of analyzing new problems to determine whether to
         abandon them or work on them. It doesn't involve actually fixing
         bugs.
<ShawnRisk> I think two things should happen with this item: 1.) We should
            research how others do this, and 2.) Change our tags for tickets.
                                                                        [11:26]
<pythonsnake> ayleph++
<AVRS> Past bugdays had "triage" mean looking through any unconfirmed bugs,
       sometimes in a particular component.
<paroneayea> ayleph: yeah, I think we're doing things in a very different way
             than most projects.
<ayleph> Are you guys trying to actually fix bugs on this "triage day" or just
         sort bugs?
<ShawnRisk> ayleph: we do both
<paroneayea> which might be part of the issue                           [11:27]
<ShawnRisk> paroneayea: we can change that up
*** tumulte (~smuxi@ALyon-651-1-231-18.w90-14.abo.wanadoo.fr) has joined
    channel #mediagoblin
<AVRS> The Firefox UNCO Untriaged triage on Tuesday is more about getting bugs
       out of the list.
<paroneayea> people usually can't get to fixing things on a day specifically.
<AVRS> Though of course we try to reproduce them, find duplicates etc.
<ShawnRisk> I think that we need to add another milestone               [11:28]
<ShawnRisk> or tag
<ShawnRisk> oh wait we already have that
<paroneayea> okay, we need to move on soon, we've spent almosst half of this
             meeting on this.  I think we need to move this conversation over
             to the wiki or mailing list and resolve to make some changes to
             our workflow by the next meeting
<Elrond> ShawnRisk - tag for what?
<paroneayea> my suggestions right now:
<paroneayea>  - compile some notes on how other projects are doing triaging
             (it's clearly very different from what we're doing)        [11:29]
<paroneayea>  - probably change our states to more reflect the states django
             uses on their trac?
<paroneayea>  - with that list made, have some more conversation on next
             triage day deciding how we want to move forward?
<paroneayea> is that good?
<pythonsnake> yes                                                       [11:30]
<ShawnRisk> my suggestion is: on every other thursday we look at enhancements,
            and then once a month we look at actually fixing bugs.  We also
            look at other projects and how they do this.  Last we look int
            tagging our tickets better.
<ShawnRisk> everything sounds good, lets move on
<ayleph> a monthly bug squashing day/weekend sounds good.
<ShawnRisk> Elrond: tags means Keywords sorry                           [11:31]
<paroneayea> http://wiki.mediagoblin.org/TriageWorkflow
<paroneayea> here
<pythonsnake> wut, I try to fix bugs everyday
<paroneayea> pythonsnake: that's good, ayleph means a more coordinated kind of
             community sprinting on it I think
<ShawnRisk> yep that is what I would say
<paroneayea> not that we shouldn't fix bugs every day :)
<ayleph> paroneayea: yeah, that.
<ShawnRisk> lets move on
<paroneayea> okay great                                                 [11:32]
<paroneayea> whew!  not much time
<paroneayea> someone put "Upgrading Trac to 1.0" on our agenda
<pythonsnake> fasterer
<ShawnRisk> I did
<paroneayea> it looks like simonft is not here, but he claimed that ticket
             already
<paroneayea> and recently he updated our wiki to have textcha (YES!  Go
             simonft :)) and added self-signed (actually, monkeysphere signed)
             ssl certs
<ShawnRisk> that is amazing                                             [11:33]
<paroneayea> so I think the person working on it is not here, but he's doing
             awesome stuff
<ShawnRisk> okay we can move on if you feel this is covered
<paroneayea> we should be having another meeting at my apartment next week;
             he's a madison local
<paroneayea> yep
<paroneayea> * Next release: 0.3.3 
<paroneayea> big topic!
<paroneayea> well kinda
<paroneayea> we're almost at freeze
<paroneayea> we were supposed to be frozen on monday :)
<paroneayea> there's only one "big ticket" that's waiting
<ShawnRisk> can we say Monday is frozen?
<paroneayea> and that's the "don't transcode video thing if we don't need to"
             thing
*** aegibson (62eae098@gateway/web/freenode/ip.98.234.224.152) has quit: Quit:
    Page closed                                                         [11:34]
<ShawnRisk> as in nothing new can be added to the milestone?
<paroneayea> that's already true that nothing new can be added
<Elrond> ShawnRisk - That's how a freeze works, right. Only bugfixes.
<paroneayea> frozen in this instance means no more features added
<paroneayea> only bugs
<paroneayea> right
<paroneayea> and we release a week later
<paroneayea> so!
<ShawnRisk> oh
<paroneayea> I have to finish this "don't transcode videos" bug.  We discussed
             a bunch of changes
<paroneayea> I will try to do them all between today and tomorrow.
<paroneayea> also!
<ShawnRisk> Monday is release?                                          [11:35]
<paroneayea> if anyone has cloudfiles access
<paroneayea> no no, freeze
<ShawnRisk> okay
<Elrond> next monday: freeze.
<paroneayea> that means that we have a week just to fix noticed bugs and for
             people to translate
<paroneayea> here:
<Elrond> then: Test, test, fix serious bugs, test, test
<Elrond> Monday in one week: Release
<paroneayea> if anyone has time
<paroneayea> http://issues.mediagoblin.org/ticket/419                   [11:36]
<paroneayea> and has cloudfiles access 
<paroneayea> this is the other one I'd *really* like in the release.
<paroneayea> but someone needs to test the cloudfiles thing
<paroneayea> I'm busy with the transcoding stuff
<ShawnRisk> what are cloudfiles again?
<paroneayea> ShawnRisk: it's a storage backend
<paroneayea> basically
<ShawnRisk> ok
<paroneayea> it's really openstack swift
<Elrond> ShawnRisk - Store your files on a remote server.
<AVRS> I don't understand the API and am not really willing to try to use it,
       but I want to translate — could there be more comments about the
       strings?
<paroneayea> yeah
<ShawnRisk> I have never used that word
<paroneayea> AVRS: you can ask about specific strings and I (or someone else
             around) can help look them up and provide context I think  [11:37]
<AVRS> ok
<paroneayea> so anyway
<Elrond> AVRS - Just ask on the channel, if a string feels strange.
<paroneayea> if I don't get this transcoding thing done by monday
<paroneayea> we freeze anyway.
<paroneayea> I think I will though.
<ShawnRisk> yep
<ShawnRisk> lets move on
<paroneayea> cool.
<paroneayea> yep
<paroneayea> next topic!
<Elrond> Yep.
<paroneayea> * Consider have release dates? 
<paroneayea> So we kind of do-ish                                       [11:38]
<ShawnRisk> I added that
<ShawnRisk> I mean can we put release dates under the milestone?
<Elrond> If someone wants to work on this cloudfiles thing, talk to me. I have
         some thoughts on it.
<paroneayea> we usually agree at the meeting.  It's "bimonthly, at the first
             monday of the month" is what we shoot for
<paroneayea> ahhh
<ShawnRisk> for 0.3.3 we have none
<paroneayea> ShawnRisk: yeah okay, I see
<AVRS> was it not monthly?
<AVRS> ah, release dates are bimonthly?
<Elrond> AVRS - It was monthly in the beginning. We once switched to
         bimonthly.                                                     [11:39]
<AVRS> ok, monday
<paroneayea> yeah mediagoblin is too big for monthly now
<paroneayea> every month everyone was so exhausted
<ShawnRisk> paroneayea: can we also put a date up for 0.3.4?
<Elrond> AVRS - With one week of freeze that monthly is just too stressy.
<AVRS> sorry, I slipped
<paroneayea> we'd knock out a release, have a week or two to get in features,
             prep for the release
<paroneayea> ShawnRisk: sure, put down may 6                            [11:40]
<paroneayea> okay
<ShawnRisk> okay moving on
<paroneayea> so resolved :)
<paroneayea> next one!
<paroneayea> Plugin stystem 
<paroneayea> stystem?? ;)
* paroneayea typo'ed
<ShawnRisk> stystem is the word we use from now o
<ShawnRisk> on*
<paroneayea> ;)
<Elrond> ;)
<pythonsnake> someone ping me when you move to gst1.0 topic please :D
<Elrond> "Mediagoblin is different" ;-)                                 [11:41]
<paroneayea> meddleware ;)
<paroneayea> so we talked about
             http://lists.mediagoblin.org/pipermail/devel/2013-February/000426.html
<paroneayea> er
<paroneayea> well at least, I wrote it up, and some of us discussed it in here
<ShawnRisk> What is left with the plugin system to get this done?
<paroneayea> ShawnRisk: lots to be written; everything on that page!
<ShawnRisk> oky
<paroneayea> there's the "already done" at the bottom
<paroneayea> aside from that..
<paroneayea> it seems like people are fairly happy about the proposal?  the
             main thing is that after this release ends, this will be my main
             focus.                                                     [11:42]
<ShawnRisk> can we have a wiki on the plugin system
<ShawnRisk> like a to-do list and other things
<paroneayea> there is a wiki page
<Elrond> I haven't read the proposal in details. I might ping paroneayea after
         the meeting about it.
<paroneayea> http://wiki.mediagoblin.org/PluginSystemDesignDocument
<ShawnRisk> oh we do oops
<paroneayea> and there's also a pluginapi tag
<paroneayea> in the tracker
<paroneayea> so you can find *most* of the things I've put up there, I also
             put in issues.                                             [11:43]
<ShawnRisk> good to know
<paroneayea> well, plugin will be my focus, in addition to the conference and
             sprint stuff this month; I want to discuss that.
<Elrond> Oh, we should add the pluginapi tag to your official tag-list. ,)
<Elrond> ;)
<paroneayea> the plan is that we knock out plugin infrastructure
<paroneayea> and then the next focus after that is figuring out federation.
<paroneayea> maybe with a release in-between to clean things up while I'm
             thinking through federation stuff.                         [11:44]
<Elrond> <devil's advocate>When is federation planned</devil's advocate>
<Elrond> Ahh, i'm too late. ,)
<Elrond> ;)
<paroneayea> Elrond: so my plan is as soon as 0.3.4 is released, I install
             pump.io
<paroneayea> and start playing with it.
<ShawnRisk> is plugin going into 0.3.4?
<paroneayea> also I just BOLDLY renamed 0.3.4 to 0.4.0!
<paroneayea> yes                                                        [11:45]
<Elrond> paroneayea - So maybe call it 0.4--plugins, 0.5--first-federation ?
<paroneayea> 0.4.0 is the Release Of The Plugin :)
<paroneayea> Elrond: yes exactly
<paroneayea> actually
<Elrond> Sounds good.
<paroneayea> "first federation" may be 1.0!
<paroneayea> well
<ShawnRisk> paroneayea: why not add plugins in the milestone description?
<Elrond> Well, 0.5--starting-federation
<paroneayea> we might want a testing-confidence-release or something
<paroneayea> ShawnRisk: done                                            [11:46]
<ShawnRisk> paroneayea: why not make another milestone for federation be it
            0.5 or 1.0
<ShawnRisk> ?
<paroneayea> hm not a bad idea
<paroneayea> hm
<paroneayea> it might make it appear "before" 0.4.1 woudl though        [11:47]
<paroneayea> I'm going to wait on it.
<paroneayea> but maybe :)
<paroneayea> anyway, more importantly, next things
<ShawnRisk> paroneayea: we can talk about this later
<paroneayea> * Consider moving to GStreamer 1.0 
<paroneayea> I feel like it will be difficult somewhat to discuss this without
             joar here
<ShawnRisk> well what needs to be discussed?                            [11:48]
<ayleph> pythonsnake: we're onto gst1.0 topic now
<pythonsnake> Moving to gst1.0 -> moving to wheezy
<pythonsnake> ayleph: thx :D
<paroneayea> it looks like 1.0 will be in not this next debian release but the
             release afterward.
<paroneayea> so yeah, not wheezy
<paroneayea> what joar and I discussed
<paroneayea> was keeping the old (read: current) gstreamer code around for
             backwards compatibility
<paroneayea> and support both                                           [11:49]
<AVRS> http://release.debian.org/migration/testing.pl?package=gstreamer1.0
       “Not touching package due to block request by freeze (contact
       debian-release if update is needed) ”
<pythonsnake> and support ffmpeg
<paroneayea> until whatever is post-wheezy becomes stable
<paroneayea> which will be a few years
<paroneayea> pythonsnake: now that's a lot more complex ;)
<paroneayea> pythonsnake: so, ffmpeg (or, libav) is kind of its own topic
<pythonsnake> did you see the gstreamer deps?
<paroneayea> pythonsnake: I know you're really eager for it.  am I right in
             the main reason for it is because of how hard it is to build
             gstreamer on shared hosting?
<pythonsnake> because of bugs                                           [11:50]
<pythonsnake> http://issues.mediagoblin.org/ticket/529
<pythonsnake> http://issues.mediagoblin.org/ticket/460                  [11:51]
<pythonsnake> those video bugs can all be fixed with ffmpeg
<paroneayea> pythonsnake: so I'm sommmmmewhat hesitant to jump to "we should
             switch to ffmpeg because of these bugs"; a lot of time we've
             found when it's like "augh, these bugs!  let's switch libraries!"
<paroneayea> we end up switching to libraries with *different* bugs     [11:52]
<ShawnRisk> if we are going to support GStreamer and ffmpeg going forward, we
            can fix with one and then the other later if problems still
            happen.
<pythonsnake> paroneayea: then we can support ffmpeg
<pythonsnake> _and_ gst
<paroneayea> pythonsnake: that might be an option
<paroneayea> pythonsnake: one route I've considered with the plugin system
<paroneayea> is the interface design I've proposed
<paroneayea> so, kind of like the storage system we have now
<paroneayea> there might be like, a VideoTranscoder interface
<paroneayea> that gstreamer and ffmpeg both implement the API of.       [11:53]
<paroneayea> if that would work without being a huge mess, it might be a good
             way forward
<paroneayea> so, it might be best to wait to see how that works out.
<ShawnRisk> I think that is a good way forward.
<paroneayea> in the meanwhile, as elrond has pointed out, it's *possible* to
             make a tricky mediatype that would be like ffmpegvideo
<pythonsnake> I dont get it
<paroneayea> the interface or the mediatype :)                          [11:54]
<pythonsnake> I didnt touch plugins stuff yet
<pythonsnake> and 'tricky'?
<paroneayea> tricky would be the mediatype solution elrond suggested that
             already works
<paroneayea> (not the plugin system solution that doesn't exist yet)    [11:55]
<pythonsnake> where is it
<paroneayea> pythonsnake: at present, do this:
<paroneayea> read this:
<paroneayea> http://wiki.mediagoblin.org/Storage
<paroneayea> and if you haven't already, this:
             http://wiki.mediagoblin.org/Processing
<paroneayea> the media type thihng I can explain post-meeting
<paroneayea> but anyway                                                 [11:56]
<paroneayea> we can look into this.
<pythonsnake> I mean
<pythonsnake> why tricky
<paroneayea> pythonsnake: ah, because it would accept the media as one media
             type, then "convert itself" during processing into the normal
             video media type
<paroneayea> since it might as well use the normal media type display stuff
             and etc
<paroneayea> (though you could not do that too if you like and just use the
             video display templates but have entirely your own metadata)
                                                                        [11:57]
<paroneayea> pythonsnake: anyway, it's already possible if you want to make an
             ffmpegvideo media type.
<paroneayea> okay, we should move on
<paroneayea> pythonsnake and I can discuss this more later.
<pythonsnake> ok
<paroneayea> * Upcoming conferences and hackathons 
<pythonsnake> that's a lot                                              [11:58]
<paroneayea> so I'll be at pycon (but actually in a room quietly working on
             mediagoblin for most of it) this year it looks like
<paroneayea> as well as at libreplanet, where I'll be speaking
<paroneayea> not sure if any of you will be there!
<paroneayea> I'd love to see people of course :)
<pythonsnake> where is it
<paroneayea> one thing we've discussed at both is running a sprint.  It'll
             definitely happen at libreplanet, and probably at pycon
<paroneayea> pythonsnake: pycon is kind of closed out at this point but it's
             in san jose, CA                                            [11:59]
<pythonsnake> meh, cant
<paroneayea> and I'll be in town for it
<ShawnRisk> sprint?
<paroneayea> and libreplanet will be in boston
<pythonsnake> <- Europe
<paroneayea> yeah, so a coding sprint, where a bunch of people (including
             newcomers) all grab tickets and start working on things
<paroneayea> pythonsnake: ah
<paroneayea> well we could do what the django sprints do and have a
             simultaneous local + IRC sprint
<paroneayea> so there's a problem with sprints though:
<ShawnRisk> <- Canada
<paroneayea> they tend to take quite a bit of time to organize, you need good
             tickets and documentation for newcomers                    [12:00]
<paroneayea> and it's a great way to get people in
* pythonsnake gets back to fixing bugs
<paroneayea> but last year at pycon I totally dropped the ball afterwards and
             neglected reviewing a bunch of patches (that won't be as bad now,
             I have dedicated code review time)
<paroneayea> I guess one thing I'm wondering is if doing two sprints is worth
             it
<paroneayea> and if anyone is interested in helpign to search out and find
             good bitesized bugs for new hackers
<pythonsnake> that's hard                                               [12:01]
<paroneayea> yeah it is :\
<paroneayea> it's a lot of work.  It can be worth it
<paroneayea> if you prepare and follow up it can be really great, if not, it
             can be a big waste of time
<Elrond> I think, there should be only one springt. Enough work to prepare
         one...                                                         [12:02]
<paroneayea> I'm already doing the libreplanet one.  I guess I wonder if
             people think I should also do a pycon one or just the libreplanet
             one?
<paroneayea> yeah
<pythonsnake> not considering communication problems...
<Elrond> ... unless one can share work for both.
<paroneayea> Elrond: yeah okay
<paroneayea> that's how I felt also.
<paroneayea> Elrond: thanks :)
<Elrond> I can't tell, where. Maybe the one, where we either get more "new
         people, that will be productive afterwards", or the one where we get
         "most done in place". I really can't rell.                     [12:03]
<Elrond> tell.
<ShawnRisk> I think that doing two would be good but too much work.  Unless we
            had someone else to help out on the ground this is not worth it
                                                                        [12:04]
<Elrond> Will there be presentations, where one could advertise the springt?
<paroneayea> Elrond: yes before hand one can advertise it at pycon
<paroneayea> at libreplanet they're going to be making a significant deal out
             of it I think.
<ShawnRisk> I believe we need energy in the project, than more gets done from
            my view.
<paroneayea> yeah                                                       [12:05]
<paroneayea> okay, I'm convinced!
<paroneayea> I won't try to organize two probably
<paroneayea> anyway
<paroneayea> looks like meeting time is over?
<paroneayea> we managed to get through all the topics just in time :)
<Elrond> paroneayea - Take the one, where you feel better, where you think, it
         will be more fun to everybody. And will be more productive.
<paroneayea> Elrond: cool, thanks
<paroneayea> alright, I'm going to consider this meeting adjourned then
<pythonsnake> bye                                                       [12:06]
<paroneayea> great meeting everyone!
<paroneayea> very productive :)
<Elrond> Right!
<paroneayea> ---------------------
<paroneayea> MEETING LOGGING ENDS!
<paroneayea> ---------------------
